McAfee Application Control 7.x Security Technical Implementation Guide

Overview

Version	Date	Finding Count (32)			Downloads
1	2018-01-03 2017-04-07	CAT I (High): 2	CAT II (Med): 30	CAT III (Low): 0	Excel	JSON	XML

STIG Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Available Profiles

Classified	Public	Sensitive
I - Mission Critical Classified	I - Mission Critical Public	I - Mission Critical Sensitive	II - Mission Support Classified	II - Mission Support Public	II - Mission Support Sensitive	III - Administrative Classified	III - Administrative Public	III - Administrative Sensitive

Findings (MAC III - Administrative Sensitive)

Finding ID	Severity	Title	Description
V-74211	High	The Solidcore client Command Line Interface (CLI) must be in lockdown mode.	By default, when an endpoint's Solidcore installation is managed by the ePO server, the CLI will automatically be in lockdown mode. This will ensure the endpoint receives all of its Solidcore...
V-74213	High	The Solidcore client Command Line Interface (CLI) Access Password must be changed from the default.	The Solidcore client can be configured locally at the CLI, but only when accessed with the required password. Since the McAfee Application Control configuration is to be managed by ePO policies,...
V-74225	Medium	The McAfee Application Control Options Advanced Threat Defense (ATD) settings must not be enabled unless an internal ATD is maintained by the organization.	This option will automatically send files with a specific file reputation to ATD for further analysis. This option is not selected by default and must only be selected if an ATD is being used.
V-74227	Medium	The McAfee Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be configured to send all binaries with a reputation of Might be Trusted and below for analysis.	When the file reputation of "Might be Trusted" is configured for being forwarded to ATD, all files with the reputation of "Might be Trusted", "Unknown", "Might be Malicious", "Most Likely...
V-74221	Medium	The Solidcore client Command Line Interface (CLI) Access password complexity requirements must be documented in the organizations written policy.	The Solidcore client can be configured locally at the CLI, but only when accessed with the required password. The misuse of the CLI would open the system up to the possible configuration,...
V-74223	Medium	The McAfee Application Control Options Reputation-Based Execution settings, if enabled, must be configured to allow Most Likely Trusted or Known Trusted only.	When a file is executed on an endpoint, the Application Control performs multiple checks to determine whether to allow or ban the execution. Only files with a reputation of "Most Likely Trusted",...
V-74219	Medium	The use of a Solidcore 7.x local Command Line Interface (CLI) Access Password must be documented in the organizations written policy.	The Solidcore client can be configured locally at the CLI, but only when accessed with the required password. Since the McAfee Application Control configuration is to be managed by ePO policies,...
V-74229	Medium	The McAfee Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be configured to only send binaries with a size of 5 MB or less.	Since binaries can be large, the file size must be limited to avoid congestion on the network and degradation on the endpoint when sending the binaries to the ATD.
V-74247	Medium	The McAfee Applications Default Rules policy must be part of the effective rules policy applied to every endpoint.	To ensure Solidcore clients are only configured to STIG and organization-specific settings, organization-specific ePO policies must be applied to all organization workstation endpoints. The...
V-74209	Medium	The Solidcore client must be enabled.	The Application Control whitelisting must be enabled on all workstation endpoints. To enable Application Control, the Solidcore client needs to be in enabled mode.
V-74243	Medium	The McAfee Application Control Options Inventory interval option must be configured to pull inventory from endpoints on a regular basis not to exceed seven days.	When McAfee Application Control is deployed on a system, it creates a whitelist of all executable binaries and scripts present on the system. The whitelist contains all authorized files, and only...
V-74241	Medium	The McAfee Application Control Options Inventory option must be configured to hide OS Files.	By default, the Windows operating system files are excluded from the inventory. By selecting this option, the overwhelming the inventory with legitimate Windows Files in the <system drive>\Windows...
V-74203	Medium	The configuration of features under McAfee Application Control Options policies Enforce feature control must be documented in the organizations written policy.	By default, the McAfee Application Control prevents installation of ActiveX controls on endpoints, enforces memory protection techniques on endpoints, and prevents MSI-installers from running on...
V-74201	Medium	The McAfee Application Control Options Advanced Threat Defense (ATD) settings, if being used, must be confined to the organizations enclave.	Data will be leaving the endpoint to be analyzed by the ATD. Because data could feasibly be intercepted en route, risk of outside threats is minimized by ensuring the ATD is in the same enclave as...
V-74207	Medium	The organizations written policy must include procedures for how often the whitelist of allowed applications is reviewed.	Enabling application whitelisting without adequate design and organization-specific requirements will either result in an implementation which is too relaxed or an implementation which causes...
V-74205	Medium	The organizations written policy must include a process for how whitelisted applications are deemed to be allowed.	Enabling application whitelisting without adequate design and organization-specific requirements will either result in an implementation which is too relaxed or an implementation which causes...
V-74249	Medium	A copy of the McAfee Default Rules policy must be part of the effective rules policy applied to every endpoint.	To ensure Solidcore clients are only configured to STIG and organization-specific settings, an organization-specific ePO policies must be applied to all organization workstation endpoints. The...
V-74233	Medium	The McAfee Application Control Options policy must be configured to disable Self-Approval.	The McAfee Application Control Self-Approval feature allows the user to take an action when a user tries to run a new or unknown application.
V-74231	Medium	Organization-specific McAfee Applications Control Options policies must be created and applied to all endpoints.	To ensure Solidcore clients are only configured to STIG and organization-specific settings, organization-specific ePO policies must be applied to all organization workstation endpoints rather than...
V-74237	Medium	The McAfee Application Control Options policies Enforce feature control memory protection must be enabled.	By default, the McAfee Application Control prevents installation of ActiveX controls on endpoints, enforces memory protection techniques on endpoints, and prevents MSI-installers from running on...
V-74235	Medium	The McAfee Application Control Options policy End User Notification, if configured by organization, must have all default variables replaced with the organization-specific data.	The "User Message" option will show a dialog box when an event is detected and display the organization-specified text in the message.
V-74239	Medium	Enabled features under McAfee Application Control Options policies Enforce feature control must not be configured unless documented in written policy and approved by ISSO/ISSM.	By default, the McAfee Application Control prevents installation of ActiveX controls on endpoints, enforces memory protection techniques on endpoints, and prevents MSI-installers from running on...
V-74175	Medium	A McAfee Application Control written policy must be documented to outline the organization-specific variables for application whitelisting.	Enabling application whitelisting without adequate design and organization-specific requirements will either result in an implementation which is too relaxed or an implementation which causes...
V-74255	Medium	The Throttling settings must be enabled and configured to settings according to organizations requirements.	The throttling settings regulate the data flow between the clients and McAfee ePO. The value for each category defines the number of entries that will be sent to the McAfee ePO daily. Clients...
V-74199	Medium	The process by which the Solidcore client Command Line Interface (CLI) Access Password is made available to administrators when needed must be documented in the organizations written policy.	The Solidcore client can be configured locally at the CLI, but only when accessed with the required password. Since the McAfee Application Control configuration is to be managed by ePO policies,...
V-74257	Medium	The Solidcore Client Exception Rules must be documented in the organizations written policy.	When exceptions are created for applications, it results in potential attack vectors. As such, exceptions should only be created with a full approval by the local ISSO/ISSM. The organization's...
V-74251	Medium	The organization-specific Rules policies must be part of the effective rules policy applied to all endpoints.	To ensure Solidcore clients are only configured to STIG and organization-specific settings, an organization-specific ePO policies must be applied to all organization workstation endpoints. The...
V-74253	Medium	The organization-specific Solidcore Client Policies must be created and applied to all endpoints.	McAfee Application Control is deployed with default policies. To ensure the default policies are not used and that an organization knowingly configures their systems to their own configuration...
V-74197	Medium	The requirement for scheduled Solidcore client Command Line Interface (CLI) Access Password changes must be documented in the organizations written policy.	The Solidcore client can be configured locally at the CLI, but only when accessed with the required password. The misuse of the CLI would open the system up to the possible configuration,...
V-74215	Medium	The organization-specific Rules policy must only include executable and dll files that are associated with applications as allowed by the organizations written policy.	To ensure Solidcore clients are only configured to STIG and organization-specific settings, organization-specific ePO policies must be applied to all organization workstation endpoints. The...
V-74195	Medium	The Solidcore client Command Line Interface (CLI) Access Password protection process must be documented in the organizations written policy.	The Solidcore client can be configured locally at the CLI, but only when accessed with the required password. Since the McAfee Application Control configuration is to be managed by ePO policies,...
V-74217	Medium	The McAfee Application Control Options Reputation setting must be configured to use the McAfee Global Threat Intelligence (McAfee GTI) option.	If a Threat Intelligence Exchange (TIE) server is being used in the organization, reputation for files and certificates is fetched from the TIE server. The reputation values control execution at...